fix: remove continuation behavior from reference integrations - #63
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes continuation behavior from the reference integrations.
This changes failed transitions from a resumable interaction model into a rejected current-request model:
Also simplifies the reference integration layer by removing stale continuation-era code and sharing duplicated LiteLLM adapter plumbing.
Why
The previous integration examples included continuation/clarification behavior where failed transitions could leave state that was completed by a later user response.
That model is no longer part of Context Compiler.
The reference integrations should demonstrate the current enforcement boundary:
user request → compiler decision → apply or reject → preserve authoritative state
This cleanup establishes a simpler baseline before adding DirectiveDrafter + HITL flows.
Example metadata
Checklist
Notes
LiteLLM changes:
OpenWebUI changes:
This PR intentionally does not add DirectiveDrafter approval flows or HITL behavior. It only establishes the post-continuation integration baseline.